home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 22
/
Cream of the Crop 22.iso
/
os2
/
cis2101a.zip
/
CIS2.HLP
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1996-10-11
|
47KB
|
1,402 lines
ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ
The Card Inventory System/2 (CIS/2) is an OS/2 application aimed at assisting
users in the protection of the valuable cards that they typically carry, use,
or are otherwise financially or personally responsible. It does this by
providing:
An easy way to record the cards of interest to the user,
A simple procedure for noting where such cards are located, and
An easy and systematic method that can be used in reporting their loss
should one or more cards become lost or stolen,
There are service companies to which a person may subscribe which, for a fee,
will help protect that person's credit cards. Should one or more of these
cards become lost or stolen, the service company will contact the appropriate
companies for the user. The purpose of this program is to avoid the cost of
such a service company, or at a minimum, supplement this service by giving a
user better records about what cards they have and where these cards are
located.
In addition, this program allows the user to more easily keep his credit card
records current, and it can record valuable cards that cannot be handled by a
card protection service company.
CIS/2 will provide essentially the same function as a service company with the
exception that the user must make the telephone call to report a lost or
stolen card.
To use Card Inventory System/2, begin with Getting Started
For more information of the functions and facilities of CIS/2, read:
Settings
Repositories
Cards
Incidents
ΓòÉΓòÉΓòÉ 1.1. Description ΓòÉΓòÉΓòÉ
The design of this program is quite simple.
There are two types of objects in this system: cards and repositories.
Cards are things like charge cards, ATM or cash cards, personal identification
cards, and so forth.
Repositories are things like billfolds, purses, and wallets.
The object of the program is to allow the user easily define these two objects
and what objects are contained in the repositories.
It is hoped that none of the cards or repositories are ever lost or stolen, but
if that event occurs, the program uses the information that the user has
defined to:
1. Minimize the effort needed in reporting the loss,
2. Assist in protecting against unauthorized use, and
3. Aid in securing replacements.
ΓòÉΓòÉΓòÉ 1.2. Advantages ΓòÉΓòÉΓòÉ
Some of the advantages of using Card Inventory System/2 are:
Users can more easily keep a current and accurate list of all their cards
and where they are located.
Defining a card is quite simple, and moving one or more cards from one
location to another can be done through the use of drag and drop.
Should a purse or wallet be lost or stolen, the system can assist in
determining exactly what cards were contained in those items, and
therefore need to be reported, and what cards can still be used.
Important cards, other than those like credit cards and ATM cards, can be
recorded. Cards such as driver licenses, personal identifications, and
even library cards can be recorded. Then, for example, if the wallet
containing these cards is lost, the system will list these cards as lost
so that the user is reminded that applications for replacements are
required (usually in person).
Note: While service companies will handle lost or stolen credit cards,
they do not handle these types of cards. This system allows definition of
these types of cards because they are valuable to the user. More
importantly, their loss needs to be reported to avoid unauthorized use of
the user's identification.
ΓòÉΓòÉΓòÉ 1.3. System Features ΓòÉΓòÉΓòÉ
The Card Inventory System/2 provides the following functions and facilities:
Any valuable card that the user wishes to record may be defined. This
includes, but is not limited to, credit cards, cash cards, telephone
calling cards, personal identification, and courtesy cards.
The user may define as many holding places for these cards as desired.
Called repositories, these holding places are typically purses,
billfolds, and wallets, but they may be any other type of container such
as a strongbox, safe, or desk.
Users may define repositories within repositories. For example, a small
wallet containing a driver's license and personal identification and a
billfold containing credit cards, can be defined within a purse that
contains other valuable cards. In such a case, if the purse is lost or
stolen, the contents of the wallet and billfold are flagged as lost or
stolen also.
A simple procedure is defined so that if a card or repository is lost or
stolen, the user can easily report the loss. The emphasis of this
procedure is to be simple and to allow the reporting to be done quickly
with a minimum of effort on the part of the user.
The location of cards can be easily changed by specifying a new location
or using the drag/drop facility of OS/2.
When a user is given more than one of a card from a company to allow
others to charge against the same account, the system will make note of
this. If one of the cards is then lost or stolen, the system will flag
the other cards as Suspended.
Cards with a date before which the card should not be used are flagged as
Pending if the current date is earlier than that date.
Cards which have an expiration date are checked by the system, and if
they are past the expiration date, they are flagged as Obsolete.
To insure that all cards are properly recorded in the system, the user
may request an Inventory Report so the user can easily check on all
cards.
ΓòÉΓòÉΓòÉ 1.4. Terminology ΓòÉΓòÉΓòÉ
The Card Inventory System/2 attempts to remain as simple as possible by using
common terms. The user should find most of these terms familiar, or at a
minimum, easy to understand.
ΓòÉΓòÉΓòÉ 1.4.1. Cards ΓòÉΓòÉΓòÉ
Cards are what the Card Inventory System/2 is all about. They are those things
with which a user buys things, identifies themselves, or gains access to some
type of service or product. They are important, and if lost or stolen, could
expose the user to significant financial and personal liability.
In this system, the user has the ability to define different types of cards,
but Card Inventory System/2 treats all cards alike -important.
The ability of the user to define different types of cards is for clarity.
Specifying the different types of cards will make it easier for the user to
remember what card is being referenced.
While different types of cards may be defined, sometimes a card will fall into
more than one type. For example, some charge cards can be used to get cash from
an ATM machine. For these types of cards, you can select which type best
reflects your use of the card. To illustrate, suppose that you have an American
Express card that can be used to charge tickets, and at the same time, get
money from an ATM machine. You can record this card either as a charge card or
as a cash card.
ΓòÉΓòÉΓòÉ 1.4.1.1. Cash Cards ΓòÉΓòÉΓòÉ
Cash cards are forms of payment that, unlike credit cards, result in the
immediate withdrawal of funds from the user's bank when they are used.
Frequently referred to as "ATM" (Automatic Teller Machine) cards because of
their use for getting cash from a bank or other financial institution, their
use is also becoming common at businesses such as food stores and gas stations.
ΓòÉΓòÉΓòÉ 1.4.1.2. Charge Cards ΓòÉΓòÉΓòÉ
A charge card is any type of charge or credit card by which the user may
"charge" something for later payment. Unlike cash cards, use of this type of
card results in the user being "credited" with a purchase for later payment.
ΓòÉΓòÉΓòÉ 1.4.1.3. Telephone Calling Card ΓòÉΓòÉΓòÉ
A telephone calling card is typically used when charging a telephone call.
Unlike cash cards or charge cards, the use of telephone calling cards is
usually restricted to charging telephone calls only.
ΓòÉΓòÉΓòÉ 1.4.1.4. Identification ΓòÉΓòÉΓòÉ
Some cards are used only for identification. A driver's license, library card,
and courtesy cards are all forms of identification. These cards are often
valuable to the user, and they can be recorded by the system.
ΓòÉΓòÉΓòÉ 1.4.1.5. Other ΓòÉΓòÉΓòÉ
Any card which does not fit in the other defined card types can be entered as
an "Other" type of card. Video store cards, senior citizen cards, and other
miscellaneous cards can be recorded in CIS/2 by entering them as Other.
ΓòÉΓòÉΓòÉ 1.4.2. Cards Issued ΓòÉΓòÉΓòÉ
Often times more than one card is issued by a card company so that more than
one person can make use the same account. CIS/2 provides for this by allowing
you to define, at one time, up to nine cards issued by the same company with
the same number.
If, after defining a card, you receive more of the same card, you may increase
the number of issued cards by doing the following:
1. Open the repository that contains the card that is to be modified.
2. Place the mouse pointer on the card to be modified and click the right
mouse button.
3. Select Modify.
The "Card Definition" notebook for the selected card will appear.
Short cut: A card definition may be opened by simply putting the mouse
pointer on the card you wish to modify and double clicking the left mouse
button.
4. Change the number of cards issued.
5. Select the Change button at the bottom of the window.
The additional cards will be generated in the currently selected
repository.
Note: You can increase the number of cards issued by changing the Cards
Issued value, but you cannot decrease the number of issued cards. The number
of cards issued can only be reduced by deleting one or more of the defined
cards.
ΓòÉΓòÉΓòÉ 1.4.3. Dates ΓòÉΓòÉΓòÉ
When dealing with cards, the dates on the cards may range from a specific day
to a given year to no date at all. CIS/2, however, allows several forms of a
date so that it should be possible to enter any needed calendar date.
Note: Whether a date is entered and displayed using the American or European
format is controlled by the CIS/2 settings.
ΓòÉΓòÉΓòÉ 1.4.3.1. Date Formats ΓòÉΓòÉΓòÉ
Because of the variety of date formats given on cards, CIS/2 allows you to
enter and display dates in the following forms:
Month, day, and year for dates using the American form, and day, month,
year for dates using the European form.
For example: the 24th day of February can be entered as 2/24/96 (American
form) or 24/2/96 (European form).
Month and year.
Year.
No date.
ΓòÉΓòÉΓòÉ 1.4.3.2. Entering Dates ΓòÉΓòÉΓòÉ
When entering a date, you may do so by entering one, two, or three numbers. The
numbers must be separated by one or more nonnumeric characters/
If entering three number, the numbers are assumed to represent the month, day,
and year in the American format or day, month year in the European format.
(Whether American or European format is being used is controlled by the system
settings.)
All three numbers do not have to be entered, and for many cards, only the month
and year are appropriate. Therefore, if only one number is entered, it is
assumed to be a year, and if only two numbers are entered, they are assumed to
be the month and year.
ΓòÉΓòÉΓòÉ 1.4.4. Repository ΓòÉΓòÉΓòÉ
A repository is any place that can be used to store cards. A purse, billfold,
or strongbox are all examples of repositories that might contain different
types of cards.
In addition, a repository may also contain other repositories. For example, a
purse may hold charge cards and a billfold, and the billfold may hold
additional charge cards.
There is no reasonable limit on the number of repositories that can be defined
by the user.
ΓòÉΓòÉΓòÉ 1.4.5. Repository Views ΓòÉΓòÉΓòÉ
By default, a repository is viewed in detail form. That is, there is one line
in the repository window for each object in the repository.
You may select alternate views of the contents of a repository by clicking on
the Options menu and selecting the view desired. The views available are:
Detail view.
The detail view shows the icon, name, type, status, owner, and effective
dates for each object in the repository.
Tree view.
The tree view shows the contents of the repository plus, if desired, what
repositories are contained within repositories being shown.
Icon view.
The icon view shows the icon and name of each object in a repository,
listing them left to right, top to bottom.
Flowed view.
The flowed view of a repository shows the icon and name of each object in
a repository, listing them top to bottom, left to right.
ΓòÉΓòÉΓòÉ 1.4.6. Incident ΓòÉΓòÉΓòÉ
When one or more cards are lost or stolen, this is called an incident.
The system allows the user to define an incident and then note, via a move or
drag and drop, what repositories and cards were lost or stolen as a result of
that incident.
ΓòÉΓòÉΓòÉ 2. Getting Started ΓòÉΓòÉΓòÉ
Setting up the system with the information about your cards is very simple.
The easiest way to start is to use one of your billfolds, wallets or credit
card holders, whatever is available at the time, with your selection at hand,
do the following:
Open the Settings. and fill in your return address.
Define the billfold, wallet, purse, or whatever you have selected by
defining a repository.
Open the repository so that you can define the cards in that repository.
Define each card that is in your repository.
Close the repository.
Save the data you have entered.
After you have saved your work, you may do the same for other repositories
until you have defined all the cards that you wish the Card Inventory System/2
to help you protect.
Note: It is strongly recommended that at least once a year an Inventory
Report be printed, and the accuracy of the report be checked. A good time to
do this in November, prior to holiday shopping when there is the highest
incident of lost or stolen cards. By keeping your inventory current, the
reporting of lost or stolen cards, while inconvenient, is simple and can
usually be done in a short period of time and with a minimum of stress.
To perform the above, and to learn more about Card Inventory System/2, start
with any of the following subjects:
Settings.
Defining a Repository
Defining a Card
Defining an Incident
ΓòÉΓòÉΓòÉ 3. Repositories ΓòÉΓòÉΓòÉ
A repository is something that holds or contains the cards that are recorded in
the system. Repositories can represent any type of receptacle or container into
which the user places or stores cards (or other repositories containing cards).
The first step in using CIS/2 is to define a repository. Once a repository has
been defined, the user may then define the cards contained in that repository.
ΓòÉΓòÉΓòÉ 3.1. Defining a Repository ΓòÉΓòÉΓòÉ
To define a repository, complete the following steps:
1. Select the Add menu, or click the right mouse button anywhere on a blank
area of the CIS/2 window.
2. Select Repository.
A "Repository Definition" notebook will appear.
3. On page 1 (General) of the notebook:
a. Enter the name of the repository being defined. (For example, My
large wallet, or Mary's Black Purse)
b. Enter the name of the person that owns the repository.
4. On page 2 (Icon) of the notebook, if desired, select some other icon to
represent the repository being defined.
The icon may be the default, one of the system defined icons, or an icon
that is defined elsewhere in the system.
5. On page 3 (Notes) of the notebook, if desired, make any notes about this
repository.
6. When the repository information has been entered, select the Add button
at the bottom of the notebook.
ΓòÉΓòÉΓòÉ 3.2. Modifying a Repository Definition ΓòÉΓòÉΓòÉ
To modify a existing repository definition, do the following:
1. Go to the main CIS/2 window or open the repository that contains the
repository to be modified.
2. Place the mouse pointer on the repository to be modified and click the
right mouse button.
3. Select Modify.
The "Repository Definition" notebook for the selected repository will
appear.
4. Modify the repository definition as desired.
5. Select the Change button at the bottom of the window.
ΓòÉΓòÉΓòÉ 3.3. Opening and Closing a Repository ΓòÉΓòÉΓòÉ
A repository must be open in order to get to the contents of that repository.
Closing a repository is a user option, and all open repositories will be closed
automatically when the user exits CIS/2.
ΓòÉΓòÉΓòÉ 3.3.1. Open a Repository ΓòÉΓòÉΓòÉ
To open a repository, do the following:
1. Go to the main CIS/2 window or open the repository that contains the
repository to be opened.
2. Place the mouse pointer on the repository to be modified and click the
right mouse button.
3. Select Open.
Short cut: A repository can also be opened by placing the mouse pointer
on the repository to be opened and double clicking the left mouse button.
ΓòÉΓòÉΓòÉ 3.3.2. Close a Repository ΓòÉΓòÉΓòÉ
To close a repository, do the following:
1. Select the File menu.
2. Select Close.
Note: If a repository is closed, any open card or repository definition
notebooks belonging to that repository will be closed without saving any
modifications made to them. Open repositories belonging to the repository
being closed are unaffected.
ΓòÉΓòÉΓòÉ 3.4. Deleting a Repository ΓòÉΓòÉΓòÉ
Warning: Deleting a repository deletes the repository and all of its contents.
This means that if a repository being deleted contains other repositories, all
of those repositories, and their contents, are deleted also.
To delete a repository, do the following:
1. Go to the main CIS/2 window or open the repository that contains the
repository to be deleted.
2. Place the mouse pointer on the repository to be deleted and click the
right mouse button.
3. Select Delete.
Note: If you delete a repository by mistake, exit CIS/2 without saving. When
CIS/2 is restarted, the repository, plus any changes made since the last time
CIS/2 data was saved, will be restored.
ΓòÉΓòÉΓòÉ 4. Cards ΓòÉΓòÉΓòÉ
There are five types of cards that can be defined in CIS/2:
1. Cash Cards
2. Charge Cards
3. Telephone Cards
4. Identification
5. Other
Your are free to record a card under any of these categories.
ΓòÉΓòÉΓòÉ 4.1. Defining a Card ΓòÉΓòÉΓòÉ
All the information you will need is contained in the documentation that came
with your card, usually on the paper to which the card was attached when it
arrived in the mail. In many cases the important information is right on the
card.
To define a new card, complete the following steps:
1. Open the repository that is to contain the card being defined.
2. Select the Add menu, or click the right mouse button anywhere on a blank
area of the repository window.
3. Select the type of card to be defined.
A "Card Definition" notebook will appear.
4. On page 1 (Card) of the notebook, enter whatever information is available
about the card. For cash, charge, and telephone calling cards, all the
information on page 1 is especially important if the card is ever lost or
stolen.
Note: If there are multiple issues of the same card (for example, the
card company sends you two cards -- one for you and one for your spouse),
check to see if two cards are the same. If the only difference is the
name on the card, define the card only once but set the "Cards Issued"
value to the number of cards you received (as in the above example, "2").
After the card is defined, use the Same Card Number - Different Owner
procedure.
5. Page 2 (Icon) allows the user to select an icon different from the
generated default.
You may select one of the icons defined by the CIS/2 or you may designate
some other icon by giving its file name.
6. Page 3 (Lost - Page 1 of 2) contains information that is needed if the
cards is ever lost or stolen.
Enter the name of the company that owns the card, and a telephone number
to be used if to report the card as lost or stolen.
Note: The telephone number is very important if the card is lost. Most
cards have this number on them, and you should enter this number in the
"Telephone Number" field. (Having the phone number on the card is not
very handy if the card is lost.)
The address information and authorized signature are only needed if (1)
the card is lost or stolen, (2) you have reported it lost by telephone,
and (3) you want to print a letter in follow-up to your telephone call.
Some companies do not even give an address for correspondence so entering
this address can be difficult, at times. If the address is available,
enter it. If not, the incident reporting procedure will tell you what to
do to help insure your phone call is recorded without having to generate
a follow-up letter.
Technically speaking, a follow-up letter should be sent, especially when
a valuable charge or cash card is involved. However, the larger card
companies are very good about sending you follow-up letters, so the
address, while good to have, is not as important as having the telephone
number.
7. Page 4 (Lost - Page 2 of 2) is not modifiable for a new card and may be
ignored. It is applicable only if the card is later lost or stolen.
8. Page 5 (Notes) is for any notes you wish to make about this card.
9. When the card information is complete, select the Add button at the
bottom of the notebook.
ΓòÉΓòÉΓòÉ 4.2. Modifying a Card Definition ΓòÉΓòÉΓòÉ
To modify a card definition, complete the following steps:
1. Open the repository that contains the card that is to be modified.
2. Place the mouse pointer on the card to be modified and click the right
mouse button.
3. Select Modify.
The "Card Definition" notebook for the selected card will appear.
Short cut: A card definition may be opened by simply putting the mouse
pointer on the card you wish to modify and double clicking the left mouse
button.
4. Modify the card definition as desired.
Note: If the number of issued cards is greater than one, any changes
made to the card definition will be applied to all other issues of the
same card with the exception of the "Card Owner" value. Any value in this
field applies only to the card being modified. (For more about multiple
issued cards, see Same Card Number - Different Owner section of this help
documentation.)
5. Select the Change button at the bottom of the window.
ΓòÉΓòÉΓòÉ 4.3. Deleting a Card ΓòÉΓòÉΓòÉ
Deleting a card removes it from the system.
To delete one or more cards from CIS/2, do the following:
1. Open the repository that contains the card or cards to be deleted.
2. If more than one card is to be deleted, select all the cards to be
deleted.
3. With the mouse pointer on one of the cards to be deleted, click the right
mouse button.
4. Select Delete.
If you delete a card that is has more than one issue, the number of cards
issued will be reduced automatically, but the other cards are not deleted.
Note: Cards, repositories, and incidents can be deleted using this
procedures. Be cautious about deleting repositories or incidents, however,
since deleting these types of objects deletes all of the objects contained in
them.
ΓòÉΓòÉΓòÉ 4.4. Same Card Number - Different Owner ΓòÉΓòÉΓòÉ
When you get more than one card from a card company at the same time, and if
the number on all the cards are the same, do the following:
1. Define the card (using the Defining a Card procedure).
2. Set the number of cards issued to the number of cards received.
3. If the name is not the same on all cards, pick one of the names and use
it to when defining the card to the system.
4. When you select the Add button, the number of cards selected will be
generated in the repository that you are using.
5. If the name is not the same on all cards, for each card with a different
name than that specified, do one of the following:
a. Open each card you want to correct and change the name. After the
name is changed, select the Change button.
b. Place the mouse pointer on the Owner, hold down the Alt key, and
click on the left mouse button. The owner name field will become
modifiable, and you may change the name of the owner directly.
6. After the cards have been generated, and the names changed, you may move
them to the appropriate repository.
Normally, when multiple cards are issued, they will be put in
repositories owned by different people. Therefore, be sure to move the
cards to their respective repositories.
ΓòÉΓòÉΓòÉ 5. Moving a Card, Repository, or Incident ΓòÉΓòÉΓòÉ
Cards, repositories, and incidents may be moved about as desired. If, for
example, you get a new wallet, you can move the cards from the old wallet to
the new one. In other cases, when you define multiple issues of the same card,
if one of cards is to be kept in a billfold and the other in a purse, you can
move one of the card issued to the billfold and the other to the purse.
When an incident is defined, what is lost or stolen is not known. After you
define an incident, you indicate what is lost or stolen by moving the cards and
repositories to the incident. As soon as the cards and repositories are dropped
in, or moved to, the incident, they are flagged as lost or stolen, and
reporting them as missing is then allowed.
Conversely, after you move a repository to an incident, there may be one or two
cards in that repository that were not lost or stolen because, as an example,
you had moved them somewhere else and had not updated the CIS/2 records. In
this case, you can move the cards not lost from the incident to where they
really are at the moment.
ΓòÉΓòÉΓòÉ 5.1. Moving Within the Same Repository or Incident ΓòÉΓòÉΓòÉ
Cards and repositories, when created, are added to the end of the repository
being used for defining them. (That is to say, the are placed in the repository
that was used to open a card definition.) If you wish, you may rearrange them
my dragging them to the place in the repository you wish them to appear.
Note: Because it is not always possible to keep all records current, CIS/2
allows you to perform a number of actions on an incident that are identical to
a repository. You may add cards and repositories to an incident in exactly the
same manner that you add them to repositories. The only difference is that an
incident cannot be added or moved to another incident.
ΓòÉΓòÉΓòÉ 5.2. Moving From One Repository to Another ΓòÉΓòÉΓòÉ
Cards, repositories, and incidents may be moved from one repository or incident
to another.
To move an object from one repository or incident to another, do one of the
following:
Drag and Drop
To move an object using the drag/drop facility of OS/2, complete the
following steps:
1. Open the repository or incident that currently contains the objects
to be moved.
2. Open the repository or incident into which you wish to move the
objects.
3. Select the objects to be moved and drag them from the first
repository to the second.
Move Option
To move an object via a pop-up menu, complete the following steps.
1. Open the repository or incident that currently contains the objects
to be moved.
2. If more than one object is to be moved, select the objects to be
moved.
3. With the mouse pointer on one of the objects to be moved, click the
right mouse button.
A pop-up menu will appear.
4. Select Move.
A list of repositories and incidents into which your selection is
allowed will appear.
5. Select the repository or incident into which you want your selected
objects to be placed.
6. The selected objects will be moved from their current repository or
incident to the end of the repository or incident that you selected.
ΓòÉΓòÉΓòÉ 6. Incidents ΓòÉΓòÉΓòÉ
When one or more cards are lost or stolen, this is an incident. Being able to
handle an incident easily and with a minimum amount of stress is one of the
major reasons that Card Inventory System/2 was created, and it is the one
feature that it is hoped you never have to use.
There are two parts to handling an incident.
1. Defining an incident
2. Reporting lost or stolen cards
In support of this, there are also a Incident Reporting Worksheet report that
can be used as an alternate method for reporting lost or stolen cards.
ΓòÉΓòÉΓòÉ 6.1. Defining an Incident ΓòÉΓòÉΓòÉ
To define an incident, go to the main CIS/2 window and complete the following
steps:
1. Select the Add menu, or click the right mouse button anywhere on a blank
area of the CIS/2 window.
2. Select Incident.
The incident definition panel will appear.
3. Enter a descriptive name of the incident.
4. Enter the date of the incident.
If you are unsure exactly what day the card or cards were lost, it is
recommended that you use the earliest possible date.
5. Enter the time of the incident.
Note: The time of the incident is for your use only, and is not used or
referenced in any follow-up letter. It might be important, later, if you
are trying to determine which charges occurred before an incident and
which occurred after.
6. Make any notes about the incident. This might include some particulars
about the incident that you want to be sure to remember.
7. Select Add to add the incident.
ΓòÉΓòÉΓòÉ 6.2. Modifying an Incident Definition ΓòÉΓòÉΓòÉ
To modify an incident definition, do the following:
1. Go to the main CIS/2 window or open the repository that contains the
incident to be modified.
2. Place the mouse pointer on the incident to be modified and click the
right mouse button.
3. Select Modify.
The "Incident Definition" window for the selected incident will appear.
4. Modify the incident definition as desired.
5. Select the Change button at the bottom of the window.
ΓòÉΓòÉΓòÉ 6.3. Indicating What is Lost or Stolen ΓòÉΓòÉΓòÉ
After you have defined an incident, you should do the following:
1. Move all the repositories or cards that were lost or stolen to the
incident.
2. If additional cards were lost or stolen (cards which are shown in other
repositories but should have been in one of those lost), move those cards
to the incident.
3. If additional cards were lost but not defined to the CIS/2, define these
additional cards to the incident.
4. If one or more cards were really not in one of the lost or stolen
repositories, move those cards out of the incident to the correct
repository.
ΓòÉΓòÉΓòÉ 6.4. Reporting Lost or Stolen Cards ΓòÉΓòÉΓòÉ
You may report the cards as lost or stolen by using the CIS/2 generated display
or working off of an Incident Worksheet Report. Since you do the same thing
whether you use a worksheet or the CIS/2 generated display, the following
procedure can be used once you have defined an incident.
1. Go to the main CIS/2 window or open the repository that contains the
incident to be processed.
2. Place the mouse pointer on the incident to be opened and click the right
mouse button.
3. Select Open.
Short cut: An incident can also be opened by placing the mouse pointer on
the incident to be opened and double clicking the left mouse button.
4. If you wish to work from a worksheet, do the following:
a. Select the Print menu.
b. Select Worksheet.
c. Select the printer to be used.
d. Select Print.
e. Use the printed report to report the cards lost or stolen.
5. If you wish to work from the CIS/2 generated displayed, do the following:
a. Select the File menu.
b. Select Report Incident.
c. Use the list of "Lost or Stolen Items" given in the upper left hand
corner of the window to step through the cards to be reported.
6. For each card, call the number indicated and report the card lost or
stolen. All the needed information to make the call and answer the
questions concerning the loss should be displayed on the screen or
worksheet.
When reporting a card as lost or stolen, do the following:
a. Note the date and time when you make the call.
b. Note the name of the person to whom you talk.
Note: This is important. In the absence of a follow-up letter,
being able to state with the particulars of the call will usually
carry as much weight as a follow-up letter, especially if you can
name the person to whom you spoke.
c. Make any notes about the call that seem appropriate. For example,
are they sending you a replacement, what charges did you verify as
being done by you, and so forth.
d. If you are using the CIS/2 generated display as you report the cards
lost or stolen, you may generate a follow-up letter before
proceeding to the next card.
If you wish a follow-up letter, select the Print button.
For more on follow-up letters, see: Follow-up Letters
Note: If you are using the CIS/2 generated displays, when you are finished
reporting, do the following:
1. Select End,
2. Select the File menu.
3. Select Save.
ΓòÉΓòÉΓòÉ 6.5. Deleting an Incident ΓòÉΓòÉΓòÉ
Deleting an incident removes the incident and all the objects indicated as lost
or stolen.
To delete an incident, do the following:
1. Go to the main CIS/2 window or open the repository that contains the
incident to be deleted.
Note: If you want a printout of the incident for your permanent records,
do the following before deleting the incident:
a. Place the mouse pointer on the incident and double click the left
mouse button.
b. Select the Print menu.
c. Select Worksheet.
d. Select the printer to be used.
e. Select Print.
f. Select the File menu.
g. Select Close.
2. Place the mouse pointer on the incident to be deleted and click the right
mouse button.
3. Select Delete.
ΓòÉΓòÉΓòÉ 7. Printed Output ΓòÉΓòÉΓòÉ
There are several types of printed output available to the user. They are
designed to assist in using the system and keeping it current.
All printed output, with the exception of the Incident Reporting Worksheet and
Follow-up Letters, can be previewed before printing.
The available printed output are:
1. Summary Report.
2. Detail Report.
3. Inventory Report.
4. Incident Reporting Worksheet.
5. Follow-up Letters
ΓòÉΓòÉΓòÉ 7.1. Summary Report ΓòÉΓòÉΓòÉ
A Summary Report is a simple list that shows what is defined in each repository
and incident beginning with the repository or incident currently selected. If
the main CIS/2 window is selected, the summary report will be a full report
showing the contents of all repositories and incidents defined to the system.
To print a Summary Report, do the following steps:
1. Select the Preview or Print menu from the CIS/2 window to be processed.
2. Select Summary.
ΓòÉΓòÉΓòÉ 7.2. Detail Report ΓòÉΓòÉΓòÉ
A Detail Report is a full list of the contents of each repository, with all the
information recorded about each object in each repository beginning with the
repository currently selected. If the main CIS/2 window is selected, the detail
report will be a full report showing, in detail, the contents of all
repositories and incidents defined to the system.
To print a Detail Report, do the following steps:
1. Select the Preview or Print menu from the CIS/2 window to be processed.
2. Select Detail.
ΓòÉΓòÉΓòÉ 7.3. Inventory Report ΓòÉΓòÉΓòÉ
An Inventory Report lists all the cards recorded in the system. This report
lists all repositories defined for a given owner, and for each repository, all
the cards that have been recorded as contained in that repository.
This report is designed so that each owner can get his or her own part of the
report, and using that part of the report, verify that the system has
accurately recorded all the the cards in their possession.
To print an Inventory Report, do the following:
1. From any CIS/2 window, select the Preview or Print menu.
2. Select Inventory.
ΓòÉΓòÉΓòÉ 7.4. Incident Reporting Worksheet ΓòÉΓòÉΓòÉ
An Incident Reporting Worksheet report can only be printed in support of an
incident.
CIS/2 allows the user to use the computer to report lost and stolen cards, and
at the same time, record this reporting activity. Some people are more
comfortable using a list of who to call, and with a pencil and paper, making
the necessary notes about the call.
The Card Inventory System/2 allows you to sit at your computer and report the
lost or stolen cards using a displayed list of who needs to be called and what
needs to be reported. Because CIS/2 recognizes that not all people like to use
this method, CIS/2 provides for the use of a printed list that gives the same
information and lets the user work from some place that might be more
convenient than the computer. Some people may even prefer to use a combination
of computer display and the printed worksheet report.
In any case, a Card Inventory System/2 Incident Reporting Worksheet will
provide a printed list that allows you to report a lost or stolen card without
necessarily using the computer at the same time.
The worksheet tells what you recorded as the name, date, and time of the
incident. Then, for each card indicated as lost or stolen, it tells you the
company to call, the phone number to use, and what needs to be reported. In
addition, space is provided for you to record when you made the call, who you
contacted, and the results of that call.
Note: When you have finished with the worksheet, it is recommended that you
transfer your notes to CIS/2 for later reference. If you plan to print
follow-up letters, you must do this so that the data needed for the letters are
available to the system.
ΓòÉΓòÉΓòÉ 7.5. Follow-up Letters ΓòÉΓòÉΓòÉ
A follow-up letter is simply a way of protecting yourself should your lost or
stolen notification not get processed. The likelihood of this varies with the
company, and most of the major card companies have excellent procedures for
handling wayward cards.
For those that like to send written notification, therefore, CIS/2 provides for
the generation of follow-up letters.
ΓòÉΓòÉΓòÉ 7.5.1. Requirements for Printing Follow-up Letters ΓòÉΓòÉΓòÉ
A follow-up letter can only be generated under the following conditions:
1. The complete address of the card company has been supplied in the card
definition.
2. An authorized signature is given in the card definition
3. A return address is given in the Settings
4. The card has been reported lost or stolen, by phone, and the date of the
telephone call has been recorded.
If a follow-up letter can be printed, the Print button on the incident
reporting display will be active.
ΓòÉΓòÉΓòÉ 7.5.2. Processing Follow-up Letters ΓòÉΓòÉΓòÉ
After a follow-up letter has been printed, the person indicated as authorized
to sign the letter should sign it and mail it.
After the letter is mailed, do the following:
1. Select the File menu.
2. Select Report Incident.
3. Use the list of "Lost or Stolen Items" given in the upper left hand
corner of the window to select the cards that have had a follow-up letter
mailed.
4. Select the Yes button.
5. Make any adjustments to the date posted.
Note: The date that a follow-up letter is posted is only used as a means of
remembering if and when the letter was sent.
ΓòÉΓòÉΓòÉ 8. Settings ΓòÉΓòÉΓòÉ
The settings contains information that applies to all of Card Inventory
System/2. In particular, it contains the following:
1. Your return address.
This information is only needed if one or more cards are lost or stolen,
the loss has been reported by telephone, and a follow-up letter is to be
printed. While not important to setting up Card Inventory System/2,
putting the return address into Card Inventory System/2 at the start
avoids having to do it should you become busy reporting a loss.
2. The format to be used when hours and minutes is entered or displayed in a
time field.
3. The format to be used when a date is formatted. That is, whether the
American or European form is to be used.
To change any of this data, perform the following:
1. Select the File menu.
2. Select Open Settings.
3. Make any desired changes to the settings.
4. Select Save.
ΓòÉΓòÉΓòÉ 9. Exiting CIS/2 ΓòÉΓòÉΓòÉ
The user may exit Card Inventory System/2 by doing the following
1. Select the File menu.
2. Select one of the following options:
a. Exit to leave CIS/2.
Note: If you have made any changes to the CIS/2 data, and those
changes have not yet been saved, you will get a warning message and
an opportunity to save before you exit.
b. Save & Exit to save the changes that have been made and exit CIS/2.
Note: This option is not available if no changes have been made.
ΓòÉΓòÉΓòÉ 10. Saving CIS/2 Data ΓòÉΓòÉΓòÉ
Nothing that the user does is saved until the user says to save the data. This
saving may be done at any time.
To save the data you have put into CIS/2, do the following:
1. Select the File menu.
2. Select Save
Note: The Save option is not available if no changes have been made to the
CIS/2 data.
ΓòÉΓòÉΓòÉ 11. Registration ΓòÉΓòÉΓòÉ
This program is not FREEWARE. Registration fee is $15 U.S. per copy.
To register your copy of Card Inventory System/2 and receive your Registration
Key, order CIS/2 from BMT Micro or RKE Consulting, Inc..
Ordering from RKE Consulting, Inc..
Ordering from BMT Micro.
ΓòÉΓòÉΓòÉ 11.1. Ordering from RKE Consulting, Inc. ΓòÉΓòÉΓòÉ
To order from RKE Consulting, Inc., send $15 (plus $1.09 sales tax if you are a
resident of Texas) drawn on a U.S. bank to:
RKE Consulting, Inc.
P.O. Box 11569
Spring, TX 77391-1569
Please indicate whether you would like your Registration Key sent by normal
mail (i.e., snail-mail) or E-mail, and include the address to be used.
To order by credit card, please send your orders to BMT Micro.
ΓòÉΓòÉΓòÉ 11.2. Ordering from BMT Micro ΓòÉΓòÉΓòÉ
To order from BMT Micro, use the following BMT Micro ordering information:
Mail Orders To: BMT Micro
PO Box 15016
Wilmington, NC 28408
U.S.A.
Voice Orders: 8:00am - 7:00pm EST (-5 GMT)
(800) 414-4268 (orders only)
(910) 791-7052
Fax Orders: (910) 350-2937 24 hours / 7 Days
(800) 346-1672 24 hours / 7 Days
Online Orders via modem: (910) 350-8061 10 lines, all 14.4K
(910) 799-0923 Direct 28.8K line
Ordering and general ordering questions:
Via AOL: bmtmicro
via MSN: bmtmicro
Via Prodigy: HNGP66D
via Compuserve: 74031,307
via Internet: orders@bmtmicro.com
telnet@bmtmicro.com
http://www.bmtmicro.com
We accept Visa, Mastercard, Discover, American Express, Diners
Club, Carte Blanche, Cashiers Check, Personal Check. Personal
checks are subject to clearance. Eurochecks in DM are welcome.
DM, Sterling, and US Currency is welcome but send only by
registered mail, return receipt requested. We cannot be liable
for lost cash sent through the mail.
Purchase orders are welcome, subject to approval. The minimum
amount is $250.00.
Information for our German customers is explained in the last
paragraph of this order form.
_____________________________________________________________________
Company:_____________________________________________________________
Name:________________________________________________________________
Address:_____________________________________________________________
_____________________________________________________________
City: _______________________________State/Province: ________________
Postal/ZIP Code: ____________________Country:________________________
Phone:_______________________________________________________________
Fax: _______________________________________________________________
E-Mail #1____________________________________________________________
E-Mail #2____________________________________________________________
Product Quantity Price Number of copies
_________________________ ______________ ________________
_________________________ ______________ x ____________ = + $ _______
_________________________ ______________ x ____________ = + $ _______
_________________________ ______________ x ____________ = + $ _______
Latest Version on Diskette _____$3.00____ x ____________ = + $ _______
North Carolina Residents add 6% Sales Tax $ _______
Shipping and Handling (no quantity limit / see below) $ _______
Email - Subject to Credit Card Verification Free
Fax (USA/Canada)........................... 1.00 US
Fax (Non-North America).................... 2.00 US
Worldwide 1st Class ....................... Free
2nd Day Priority, USA Only ................ $ 4.00 US
US Postal Service International Express
(Including Canada and Mexico), allow up to
7-10 days ............................... $ 25.00 US
Airborne Select Delivery (USA Only) $ 8.00 US
FedEx Overnight, USA Only (delivery by
3:00 pm the following day) .............. $ 15.00 US
FedEx Europe/Japan (guaranteed delivery
within 3 days) .......................... $ 35.00 US
Total: $ _______
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé For credit card payment only Γöé
Γöé Γöé
Γöé Circle one: VISA / Master / Discover / American Express / Diners Γöé
Γöé Γöé
Γöé Credit card number: _____________________________________________ Γöé
Γöé Γöé
Γöé Expiration date: ________________________________________________ Γöé
Γöé Γöé
Γöé Authorization signature: ________________________________________ Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ORDERING FROM INSIDE GERMANY ONLY
=================================
Persons in Germany wishing to order shareware may also transfer funds
into our account with Deutsche Bank. Once the money is deposited you
may either fax a confirmation to us with proof of deposit or wait until
Deutsche Bank notifies us of the transaction (usually 10-18 business days).
Account information is as follows:
Deutsche Bank / Frankfurt Branch
EmpfДnger: Thomas Bradford / BMT Micro
Konto-Nummer: 0860221
Bankleitzahl: 500-700-10
When you make the transfer, be sure to put your name and the program you
are registering on the transfer.
Current exchange rates can be obtained by sending an email to
dm_to_us@bmtmicro.com. An automated reply will return todays exchange
rates.
It is very important that you send us a completed order form by
either email or fax if you deposit money into this account for a
registration. Fill the order form out as usual except in the credit
card number field put "DEUTSCHE BANK". We will file the order and
use it to match against the deposit information we receive from the
bank.
IMPORTANT!
----------
When you email us your order form, we will reply with an
acknowledgement. If you do not get an acknowledgement within 24 hours
please send your order again in case it was lost. This extra bit of
caution can save a lot of confusion.
If you are concerned that your order is taking too long to process, feel
free to check with us about the status of your order. It's important
to all of us that you feel safe doing business with our company and
please feel free to suggest ways we can improve our service to you.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Sometimes multiple-issued cards have the same basic number with a number suffix
indicating the particular card issue. For example "12345-1" and "12345-2" might
be shown as the two card numbers from the same company for account 12345. In a
case like this, the user can either (1)define two cards, or (2) define one
card, using only the basic account number, and making note about the card
number in the notes section of the definition notebook.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
This type of change can only be performed when the view of the repository is
being shown in detail view.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
You are not allowed to move an incident into another incident. You may,
however, move a repository to an incident or an incident to a repository.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The use of the main CIS/2 window is recommended but not required. Any
repository window may be used to define an incident. Since, after definition,
the incident will become an object in the window being used, the use of the
main CIS/2 window will probably be the most logical.
If you experience more than one incident, you may want to define a "repository
of incidents" which you will use to define all incidents.
Where you define an incident is up to you except that you cannot define an
incident using an incident window or a repository that is already flagged as
lost or stolen.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The phone number, like all the other information about the card, are taken from
the data that you put in the system when you defined the